Ensure PolicyRuleTarget updates in prod builds #15657
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #15652
Occurred changes and/or fixed issues
handler: 'debouncedUpdateMatches', -->debouncedUpdateMatches: debounce(this.updateMatches, 500)seems broken in prod... but not dev->
yarn dev--> fine->
yarn start:prod--> failTechnical notes summary
handler: debounce(this.updateMatches, 500),would have been neater, however fails withthisissueshandler: 'updateMatches',==> works interestingly works, so it's just scenarios where a debounced function is stored as a variable. i've had a look where this happens and the file in the PR is the only oneAreas or cases that should be tested
Setup
Create a namespace and give it a unique name + label (for example
aaa:aaa). Create a pod in that namespace and give it a unique label (for examplebbb:bbbConfigure ingress rules to restrict incoming traffic+--> clickAdd allowed traffic sourceAreas which could experience regressions
Checklist
Admin,Standard UserandUser Base